Skip to content

Compare a repository's library projects when run without a command - #78

Merged
Mpdreamz merged 1 commit into
mainfrom
projects
Nov 14, 2026
Merged

Mpdreamz merged 1 commit into
mainfrom
projects

Conversation

@Mpdreamz

Copy link
Copy Markdown
Contributor

Run without a command in a repository, assembly-differ now compares every library project's Release build with the latest release of its package. It skips test projects and projects that are not packable, and it does not build.

Prompt summary: Running assembly-differ without arguments, in a directory with a solution or project file, should report the changes by itself. That makes it easy for people and coding agents alike. It skips test projects and IsPackable=false projects, each of which a flag includes, and a project flag picks projects. Building is left to the user, with a warning when there is no build output. The --build orchestration of the github command is the tool doing too much, so it goes.

Why

To see what a change does to a library's API, a person or an agent had to know the package id, the last version, the target framework and where the build output lives, then spell all of it out. An agent checking a change usually decompiled the assemblies itself instead.

What

projects, the default command

The command reads the one .slnx or .sln in the directory through dotnet sln list, or else its project files. It asks MSBuild for IsPackable, IsTestProject, PackageId, AssemblyName and the target frameworks. For the newest framework, it finds the Release TargetPath and compares it with the latest stable release of the package on the NuGet.config feeds. Every project goes into one report. Each skipped project gets a line saying why and which flag includes it. A package with no release, or one that ships no matching assembly, such as a tool package, is reported and skipped.

No building

The tool does not build. A project without Release output is skipped with a warning that says to run dotnet build -c Release. --project picks project files explicitly, whatever kind they are. Two provider specs passed straight to the root, as before commands existed, are routed to diff, so those callers still work.

github command dropped, github| spec deprecated

The github command cloned another commit and ran a build command the user had to spell out; it merged in #75 and was never released. The github|... spec in the hidden diff still works and now warns on stderr. The README shows the replacement: git worktree add, dotnet build, then assembly-differ files.

A crash fixed

A package with no assemblies under lib/, such as one that only ships an analyzer, crashed the NuGet provider with "Sequence contains no elements". It now reports that and compares nothing.

Verify

mise run test
# ProjectsTests build a small solution for real: a library with a release on a local feed, a test project and an unpackable one
cd ~/Projects/argh && dotnet build -c Release && dotnet run --project <assembly-differ checkout>/src/assembly-differ -f net11.0 -c Release

🤖 Generated with Claude Code

Running the tool took two sources spelled out; in a repository, people and
agents want to know what changed in their libraries since the last release.
Without a command it now reads the directory's solution or project files,
skips test and unpackable projects, and compares each project's Release
build with its package's latest release. It does not build: a project
without output is skipped with a warning.

The github command, which cloned and built another commit, is dropped
before its first release; the github| spec in diff still works and points
at a git worktree recipe instead. Packages with no lib/ assemblies no
longer crash the nuget provider.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@Mpdreamz Mpdreamz added the feature A new capability (minor bump) label Nov 14, 2026
@Mpdreamz
Mpdreamz merged commit b9029aa into main Nov 14, 2026
6 of 7 checks passed
@Mpdreamz
Mpdreamz deleted the projects branch November 14, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature A new capability (minor bump)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant